home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
comm
/
xfer57.zip
/
TRANSFER.DOC
< prev
next >
Wrap
Text File
|
1992-04-20
|
14KB
|
348 lines
TRANSFER
Version 5.7
Copyright 1992-Steve Lewis
NOW with HSlink BI-DIRECTIONAL protocol! (REGISTRATION REQUIRED)
The BATCHFLE file for Version 5.7 has a different format than that used
with earlier versions of TRANSFER, in that the new version does not have
"***" tacked onto the bottom of the file list. Be SURE to remake the
BATCHFLE file, using MAKBATCH.EXE.
Version 5.7 supports the new HSlink bi-directional transfer protocol!
REGISTRATION is required to access this protocol.
The PUMA protocol has been eliminated, due to its decreasing popularity.
Version 5.7, when REGISTERED, checks all filenames (paths included), when
uploading in the manual mode. If a file is not found, the user will be
prompted to re-enter the filename. If uploading is from a floppy drive,
user is prompted if drive door is open.
Note also that TRANSFER may be used with the new GSZ.EXE and GSZ.COM
programs. To use these programs, simply rename them DSZ.EXE or DSZ.COM.
Version 5.7 of TRANSFER is distributed in its NONREGISTERED state. By
registering TRANSFER, you will receive a file named "AUTHORIZ". This
file contains your personal serial number and checksum, and when present in
the SAME directory as TRANSFER, it will UNLOCK the SPECIAL features of
Version 5.7. Your copy of AUTHORIZ will be compatible with ALL future
versions of TRANSFER. You will NOT need to purchase AUTHORIZ again!
These special features are;
(1) May be configured for a FIXED PROTOCOL, thus
eliminating the need to manually select the protocol.
(2) May be configured for "Hotkeys", eliminating
the necessity for carriage returns whenever
possible.
(3) When configured for BOTH the program-selectable protocol
AND the "Hotkeys" modes, a carriage return <cr> entered
in response to a question returns the user to the "Enter
protocol" line of text, permitting the user to re-enter
the protocol number.
(4) When MANUALLY entering a filename for uploading, it is
checked to make sure that it actually exists. If it
doesn't exist, the user is prompted to re-enter the
filename. If uploading is from a floppy drive, then
user is prompted if drive door is open.
(5) HSlink bi-directional protocol and Tasy protocols are
supported.
Version 5.7 of TRANSCFG.EXE prompts for the additional information, but
UNREGISTERED versions will NOT be able to take advantage of this information.
Future versions of TRANSFER will have MANY more SPECIAL features!
Version 5.7 corrects a defect in earlier versions that permitted other than
integral values to be entered for the protocol number. Additionally,
Version 5.7 does not permit the entering of a blank line for the filename.
When batch uploading with the MEGALINK protocol, A-L-L filenames MUST be
from the S-A-M-E directory! The directory of the FIRST filename MUST be the
directory for ALL the others. This limitation is due to the MLINK.EXE
PROTOCOL, and is NOT due to the "TRANSFER.EXE" program.
When changing versions of TRANSFER.EXE, A-L-W-A-Y-S change the following
files as well;
TRANSCFG.EXE
MAKBATCH.EXE
..... BECAUSE THEY MAY DIFFER FROM THOSE
PACKED WITH THE PREVIOUS VERSION OF
TRANSFER.EXE !!!
When installing a new version of TRANSFER, always RE-CONFIGURE with the
latest TRANSCFG.EXE program!
TRANSFER was written primarily as a file transfer shell for a communications
program. If you are using PCPLUS, configure PCPLUS so you can shell out
to TRANSFER by using the <ALT>J or <ALT>U keys.
TRANSFER can be used in the MODEM mode, or in the DIRECT mode by using a
"Null Modem" cable. In the MODEM mode, TRANSFER assumes that communications
have already been established by the communications program, therefore,
neither the modem nor COM port are initialized. In the DIRECT mode, the COM
port is initialized to the communications speed specified in the configuration
routine, and in addition is set to 8 data bits, 1 stop bit, and no parity.
After exiting TRANSFER in the DIRECT mode, you may want to manually reset
your COM port.
The following transfer protocols are supported by TRANSFER;
(1) Xmodem/CHK SUM
(2) Xmodem/CRC
(3) Ymodem/(1K Xmodem)
(4) Ymodem/CRC
(5) Ymodem-G
(6) Ymodem/Batch
(7) Jmodem
(8) Jmodem/Batch (NOW TRUE BATCH!)
(9) Zmodem/Batch (Z-MODEM 90)
(10) Super8K
(11) Super8K/Batch
(12) Super8K-G
(13) Super8K-G/Batch
(14) K9Xmodem
(15) K9Xmodem/Batch
(16) Cmodem
(17) Cmodem/Batch
(18) WXmodem
(19) WXmodem/Batch
(20) Tmodem/Batch
NEW! (21) HSlink/(BI-DIRECTIONAL!---REGISTRATION REQUIRED!)
(22) Nmodem
(23) Tasy/Batch (REGISTRATION REQUIRED!)
(24) Megalink/batch
(25) Hyperprotocol/CRC
(26) Hyperprotocol/Checksum
*INSTALLATION*
XFR57.ZIP contains five files;
TRANSFER.EXE
TRANSFER.DOC
TRANSCFG.EXE
MAKBATCH.EXE
MAILER
On some Bulletin Boards, the files may be contained in XFR57.LZH,
XFR57.ARC, or XFR57.PAK.
TRANSFER.EXE requires the following files to operate;
DSZ.COM (or DSZ.EXE) * (Required for Protocols #4-#6, #9) See par. 2
SUPERK.COM * (Required for Protocols #1-#3, #10-#19)
SUPERK.000 * (Comes w/SUPERK.COM) (Required for Protocols #1-#3, #10-#19)
JBATCH.COM * (Required for Protocols #7, #8)
JBA.COM * (Required for Protocols #7, #8)
TMODEM.EXE * (Required for Protocol #20)
HSLINK.EXE * (Required for Protocol #21) *(REGISTRATION REQUIRED)
NMODEM.EXE * (Required for Protocol #22)
TASY.EXE * (Required for Protocol #23) *(REGISTRATION REQUIRED)
CMODEM.EXE * (Comes w/SUPERK.COM) (Required for Protocols #16, #17)
MLINK.EXE * (Required for Protocol #24)
HYPERP.EXE * (Required for Protocols #25, #26)
TRANSFER.EXE
TRANSFER.BAT (Created by TRANSCFG.EXE)
TRANSFER.CFG (Created by TRANSCFG.EXE)
MODE.COM * (DOS file-Resides in DOS directory)
BATCHFLE (Optional. Created by MAKBATCH.EXE)
AUTHORIZ (Optional. Needed to unlock special features)
*=USER SUPPLIED!
VERY IMPORTANT---READ!!!
The TRANSFER.EXE program needs to be able to locate the TRANSFER.CFG file
in order to operate. TRANSCFG.EXE automatically creates a batch file named
TRANSFER.BAT, and places it in the root directory. This batch file
automatically changes the drive and directory to the location of the
TRANSFER.EXE and TRANSFER.CFG files, which must exist in the SAME directory.
All the transfer protocol files may exist in ONE separate directory. If
SUPERK.COM and SUPERK.000 do not exist in the same directory as TRANSFER,
then SUPERK.COM must be configured so that it can find its overlay file,
SUPERK.000. To do this, type SUPERK @, which will bring SUPERK into the
Configuration Mode, and then specify both the "wrkpath" to SUPERK.COM and the
"Ovlpath" to SUPERK.000. They must BOTH be set to point to the directory where
t